🌐 [translation-sync] FIX: seven source-side defects in python_by_example, functions, numpy and pandas - #149

✅ Deploy Preview for majestic-griffin-10b166 ready!

Name	Link
🔨 Latest commit	854f029
🔍 Latest deploy log	https://app.netlify.com/projects/majestic-griffin-10b166/deploys/6a72a3a004434a00083629cc
😎 Deploy Preview	https://deploy-preview-149--majestic-griffin-10b166.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

✅ Translation Quality Review

Verdict: PASS | Model: claude-sonnet-5 | Date: 2026-08-05
Routing: editor — 2 minor finding(s) in gating categories (accuracy/terminology/syntax/diff-check/other); accuracy 8 below floor 9; terminology 8 below floor 9
Shadow gate: would NOT auto-merge (recorded only; no action taken)

📝 Translation Quality

Summary: The translation of the modified sections (Overview, Random Draws, Recursive Function Calls, Exercises, Creating Arrays, Make Changes in DataFrames, Accessing Data with requests, While Loops) is accurate, fluent, and technically sound. Minor issues are limited to small spacing/typo slips and slightly literal phrasing in a few spots, none of which affect comprehension or build integrity. No syntax errors were found in code blocks, math, or MyST directives within the changed sections. Technical terminology (NumPy, broadcasting, DataFrame, Series, callable, etc.) is consistently kept in English/Latin script alongside accurate Persian explanations, matching the language policy. Code blocks, LaTeX math, and MyST directives (exercise-start/solution-start, code-cell, etc.) are fully preserved without structural corruption across all four changed files. The translation of nuanced concepts like keyword arguments, recursion, and broadcasting rules is accurate and mirrors the logical structure of the English source closely. Persian punctuation and formal academic register are used appropriately throughout the modified sections.

Suggestions:

• [minor · accuracy] lectures/functions.md — ### Adding Conditions: The English says 'The situation is similar for...' concept is fine, but in the Persian translation of the note about equality testing, the phrase 'عبارت a == 10 با توجه به مقدارa میتواند True یا False ارزیابی شود' is missing a space before 'میتواند' (مقدارa) which is a minor spacing/formatting slip introduced in this changed section. → عبارت a == 10 با توجه به مقدار a می‌تواند True یا False ارزیابی شود.
• [minor · fluency] lectures/functions.md — ### The Flexibility of Python Functions: The sentence ' در بخش‌های بعدی، با مثال‌هایی نشان خواهیم داد که انتقال یک تابع به یک تابع دیگر تا چه حد ساده است.' has a double space before 'ساده' which is a minor formatting/typo issue in a modified section. → در بخش‌های بعدی، با مثال‌هایی نشان خواهیم داد که انتقال یک تابع به یک تابع دیگر تا چه حد ساده است.
• [minor · terminology] lectures/pandas.md — ### Accessing Data with requests: In the 'Accessing Data with requests' section, the phrase 'اگر پیام خطایی نباشد، پس فراخوانی موفق بوده است.' is accurate, but the subsequent list translation of causes for errors ('شما به اینترنت متصل نیستید --- امیدوارم که این مورد نباشد.') slightly loses the parenthetical tone of the source ('hopefully, this isn't the case') — acceptable but could be smoother. → شما به اینترنت متصل نیستید --- امیدواریم که این‌طور نباشد.
• [minor · fluency] lectures/pandas.md — ### Make Changes in DataFrames: The heading translation list maps 'Make Changes in DataFrames' to 'ایجاد تغییرات در DataFrames', which is fine, but within the body text itself the phrase 'رصف‌های/ستون‌ها به عنوان یک کل' vs actual rendered 'سطرها/ستون‌ها به عنوان یک کل' is consistent and correct; no major issue found here besides a slightly literal translation of 'as a whole' which reads acceptably in Persian.

🔍 Diff Quality

Summary: All four target files were correctly updated in the same locations as the English source, with translated text and code both properly synced and no unrelated changes.

This review was generated automatically by action-translation review mode.

🚀 Deployed on https://6a72a4af74055b630c65079a--majestic-griffin-10b166.netlify.app

Notes from reviewing the zh-cn counterpart of this same sync round (.zh-cn#86, now merged). Two things, one pre-emptive and one that wants a native-speaker eye.

numpy.md carries two of upstream's four items, and that is correct

The zh-cn PR changed four places in numpy.md; this one changes two. That difference is not a dropped sync — the other two were already satisfied in Persian before this PR:

Worth recording because zh-cn needed a fix-up here and this edition does not: upstream's change was to add a space after its ---, and the zh-cn sync mirrored that as a space before the full-width ——, which Chinese does not take. Persian was already spaced on both sides, so the same mirroring had nothing to do.

Does the while restructure carry the semantic fix?

This is the one item I could not settle. Upstream's python_by_example.md change was specifically semantic, not stylistic — "keep executing until the condition is satisfied" was backwards and contradicted the sentence immediately after it, so it became "as long as the condition is satisfied".

In this PR the Persian sentence is reordered but both the before and after use تا زمانی که, and the following sentence also uses تا زمانی که, there carrying the "until" sense (تا زمانی که i برابر با ts_length شود). So the two adjacent sentences appear to use the same connective for the two opposite meanings that upstream deliberately separated.

I do not read Persian well enough to judge whether the reordering resolves that in context. If it does not, the fix has landed structurally without landing semantically, which is the thing #604 was actually trying to correct.

Minor

The FILO → LIFO line also quietly corrects می کند → می‌کند (ZWNJ). That is an improvement rather than scope drift, just flagging it so it is not read as an unrelated edit.